Skip to content

docs: fix ISR guide link to res.revalidate#89342

Merged
lukesandberg merged 3 commits intovercel:canaryfrom
pavan-sh:fix/isr-docs-link
Feb 5, 2026
Merged

docs: fix ISR guide link to res.revalidate#89342
lukesandberg merged 3 commits intovercel:canaryfrom
pavan-sh:fix/isr-docs-link

Conversation

@pavan-sh
Copy link
Contributor

No description provided.

@nextjs-bot nextjs-bot added the Documentation Related to Next.js' official documentation. label Jan 31, 2026
@nextjs-bot
Copy link
Collaborator

nextjs-bot commented Jan 31, 2026

Allow CI Workflow Run

  • approve CI run for commit: d661c46

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

Copy link
Contributor

@lukesandberg lukesandberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@lukesandberg lukesandberg self-assigned this Feb 5, 2026
@lukesandberg lukesandberg merged commit 2932b93 into vercel:canary Feb 5, 2026
122 of 131 checks passed
bgub pushed a commit to bgub/next.js that referenced this pull request Feb 5, 2026
<!--
Thanks for opening a PR! Your contribution is much appreciated. To make
sure your PR is handled as smoothly as possible we request that you
follow the checklist sections below.

Choose the right checklist for the change(s) that you're making:

For Contributors

Improving Documentation

• [x] Run pnpm prettier-fix to fix formatting issues before opening the
PR.
• [x] Read the Docs Contribution Guide to ensure your contribution
follows the docs guidelines:
https://nextjs.org/docs/community/contribution-guide
Fixing a bug

• [ ] Related issues linked using fixes #number
• [ ] Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
• [ ] Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md
Adding a feature

• [ ] Implements an existing feature request or RFC. Make sure the
feature request has been accepted for implementation before opening a
PR. (A discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas)
• [ ] Related issues/discussions are linked using fixes #number
• [ ] e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
• [ ] Documentation added
• [ ] Telemetry added. In case of a feature if it's used or not.
• [ ] Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md
For Maintainers

• [ ] Minimal description (aim for explaining to someone not on the team
to understand the PR)
• [ ] When linking to a Slack thread, you might want to share details of
the conclusion
• [ ] Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
• [ ] Add review comments if necessary to explain to the reviewer the
logic behind a change
What?

Fix a broken link in the ISR guide by switching to a site-absolute
/docs/... URL for the res.revalidate reference.

Why?

Without the leading /, the link can resolve as a relative path and break
depending on where it’s rendered.

How?

Update the ISR guide link target to a site-absolute
/docs/pages/guides/incremental-static-regeneration#on-demand-validation-with-resrevalidate.

Closes NEXT-
Fixes #
-->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Documentation Related to Next.js' official documentation.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants